Systems and methods for enabling anonymous collaboration among members along value chains

ABSTRACT

The invention concerns a computer-implemented collaboration platform comprising:
         means enabling an initiator ( 158 ) to create a message ( 168 );   means enabling the initiator ( 158 ) to invite a group of first degree partners ( 160, 162, 164 ) to respond to the message ( 168 );   means enabling a first degree partner ( 162 ) to create a sub-message ( 170, 172 );   means adapted to automatically create a link between the sub-message ( 170 ) and the message ( 168 ), or between the first degree partner ( 162 ) and the initiator ( 158 ), or between collaboration spaces established for the sub-message ( 170 ) and the message ( 168 ); and   means enabling the first degree partner ( 162 ) to invite a group of second degree partners ( 176 ) to respond to the sub-message ( 170 ) while concealing identities of one or more first degree partner ( 158, 160, 164 ) for the group of second degree partners ( 176 ), and/or vice versa concealing identities of one or more second degree partner ( 176 ) for the group of first degree partners ( 158, 160, 164 ).

RELATED APPLICATION

This application is a continuation of, and claims priority to and thebenefit of, co-pending PCT Application PCT/EP2012/003507, filed Aug. 17,2012, which claims priority to, and the benefit of, European ApplicationNo. 11181058.6, filed Sep. 13, 2011, and U.S. Provisional ApplicationNo. 61/525,487, filed Aug. 19, 2011, for all subject matter common tothese applications. The disclosures of said applications are herebyincorporated by reference in their entirety.

FIELD OF THE INVENTION

The present invention generally relates to collaboration betweenpartners which typically represent different individuals or entities ina value chain, e.g. a business supply chain or design/development team.Whereas the different partners in a value chain have to collaborate onvarious issues, it is not always obvious or known to the initiator whohas to be involved to solve a problem, certain confidentiality may haveto be respected, and it may be desired to keep the identities of certainindividuals or entities in the value chain anonymous. The presentinvention therefore relates to a platform (or system) and a method thatenables optionally anonymous/confidential collaboration betweenconnected teams and a convenient way of involving additional individualsor entities to collaborate in a self-directing collaborative communitywithout necessarily disclosing their identity and/or without disclosingthe identity of partners that are already involved in the collaboration.

BACKGROUND OF THE INVENTION

In value chains, e.g. supply chains, there are many individuals andentities, called partners throughout this patent application, serving avariety of roles and functions. In many instances, issues arise thatrequire the knowledge and expertise of such partners in the supply orvalue chain. Often however, there exists a desire to conceal or keephidden the identities of individuals and/or entities in the supply orvalue chain because the identity of these individuals and/or entitiesrepresents important know-how of another partner in the value chain. Inthe example where manufacturer A receives component parts from companyB, and company B receives its materials for those parts from company C,company B may wish to keep the identity of company C concealed frommanufacturer A to avoid that manufacturer A would decide to reduce costsby cutting out the middleman, i.e. company B in this example, and makethe parts itself with material supplied by company C. In addition,companies B and C may be less likely to suggest innovative or new ideasif company A is actively or even passively involved in the brainstormingprocess. This can diminish the creativity of companies B and C, therebyweakening the value of their proposed solutions.

The knowledge to solve an issue or question, is often hidden in thevalue chain, in a sense that the initiator of a question/issue does notknow the person who has the knowledge to answer. In the example above,Manufacturer A may have a question about the part received from companyB, but does not know who needs to be involved to answer the question. Itmay be company C or even company D, a supplier of company D, etc. Inmany value chains, companies have no insight in their supply chains.Thus, to respond a question/solve an issue, one needs several parties towork together, while no single party involved would be able to tell whothe entire team is. It must be possible to establish the team solvingthe issue organically, as each member of the value chain may involvejust one other member to get access to the knowledge to solve the issue.The same is true for the sales side: if company A needs to solve aquestion about the use of their products by end-users, they may need tofind the answer through the customers who on their turn invite othermembers downstream (or other stakeholders/partners) of the value chain.

The desire to maintain anonymity/confidentiality often hinders anindividual or entity's ability to reach a solution to a particularproblem. This is in particular the case when reaching such a solutionrequires collaborative involvement and knowledge of partners atdifferent points along a supply or value chain. In many situations,creative initiatives, solutions, and business plans are quashed by theinability to transfer information in an efficient manner, enabling theanonymity of the various sources of information to be respected, andenabling the confidentiality of the exchanges of anonymous or knownsources to be respected without sacrificing knowledge of the credibilityor reliability of such sources.

Existing platforms that enable collaboration between partners in a valuechain can be categorized as e-mail based platforms, project managementsystems, community platforms, ticketing systems, or supplierrelationship management (SRM) systems. All of these existing platformsare disadvantageous as will be explained in more detail below. Inparticular, none of these existing platforms enable a partner in thevalue chain enable to involve second tier or second degree partners on aproblem or sub-problem while keeping the identities of certain firsttier partners hidden for such second degree partner and vice versa.Also, these systems typically do not allow members to invite others tobecome members at their discretion, and thus do not allow to reallyoperate as self-directive connected virtual teams.

Collaboration platforms based on e-mail enable an initiator to create amessage, eventually with attachments such as Excel files or Worddocuments. The initiator can send the message to a group of first degreepartners and invite them to respond to the message. A first degreepartner can forward the e-mail message to a second degree partner, notknown or directly linked to the initiator of the message, when it isbelieved that collaboration or assistance of such second degree partnersis desired in order to be able to respond to the initial message.

Although e-mail platforms allow to structure messages through forms,enable to insert a due date for a task or response, and featureforwarding capabilities, the link between message and response is ratherweak. Usually, this link is established through the title or subject ofthe e-mail message and gets lost as soon as one partner in theforwarding chain tampers with these fields. E-mail based platformsfurther do not allow to prevent forwarding the identity of the initiatoror other first degree partners. In the reverse direction, e-mail doesnot enable to prevent disclosing the identity of the second degreepartner(s) that sourced part of the response. E-mail is furtherdisadvantageous in that it does not enable to split a message or list insub-messages thereby maintaining a link between the different elementsof the message or list.

Project management systems are software platforms that allow to managetasks within an organization, typically a corporate entity wherecross-department collaboration is required. Project management systemsenable to send tasks to users within a closed working environment. It isnot possible for users of a project management system to inviteadditional, external individuals/entities, i.e. second level partners,to collaborate. Although project management systems allow to split atask into sub-tasks and create a team per sub-task, it is not possibleto copy and forward a task or sub-task to have a different team work onthe sub-task while keeping the identities of the initial team and thedifferent team hidden to each other. Project management systems arefurther disadvantageous because they are designed and developed tomanage tasks only. They do not allow to handle the related datastructures such as structured information, questions, issues, ideas,tables, lists, etc.

Collaboration community platforms are web applications that enable usersto invite others for collaboration with respect to a topic. Suchplatforms deliver collaboration tools like a chat tool, a web-baseddiscussion space, audio/video conference tools, etc. to exchange ideas.It is however not possible to manage confidentiality within acollaboration community. The users cannot hide identities of first orsecond tier partners, and it is impossible to control the extent towhich a user is allowed to forward information that is shared withinsuch community. The known collaboration community platforms hence do notenable to conveniently split a message or inquiry in sub-messages,forward sub-messages to different teams while maintaining a link betweenthe sub-messages and the initial message, and controllingconfidentiality and concealment of identities of the partners betweenthe different teams.

Ticketing systems are developed and used to facilitate operations andbuild knowledge of a support organization. Such systems enable toforward a message, i.e. an inquiry or issue, to other users, and tomaintain a history list of already solved issues and responded messages.

Ticketing systems are however designed to constitute closed user systemsas a result of which it is not possible to invite individuals fromexternal organizations or entities to collaborate on an issue. The usersof ticketing systems typically work in small teams. They forward aticket from one user to another. It is not possible to generate lists orsplit tickets in sub-tickets and maintain a link between the initialticket and eventual sub-tickets in order to enable different teams/usersto work on sub-tickets and finally send back the solutions tosub-tickets back to the initiator. It is for sure also not possible inticketing systems to forward tickets/sub-tickets while hiding theidentity of for instance the initiator to the teams/users that areworking on the forwarded ticket or sub-ticket. Ticketing systems arefurther limited in their ability to structure information that isshared: usually, a free text solution augmented with a description fieldis provided for messaging.

Supplier relationship management (SRM) systems provide functionalityenabling to collect complex information from suppliers in the valuechain of a company. SRM systems are typically used to distributesurveys/inquiries to different potential suppliers, follow-up and reporton the comparison between the survey responses received from differentpotential suppliers. The contacted suppliers however cannot create anown workspace in such SRM system, copy inquiries or sub-inquiries andinvite others to collaborate in responding to an inquiry. The SRM systemand all information shared therein is owned and controlled by the buyerof the platform. This entity exclusively decides who can join and usethe SRM platform. As a consequence, SRM platforms do not enable a flowof information/inquiries across plural levels of the supply chain.

In summary, there is a need for systems and methods that enableanonymous collaboration among different partners, e.g. individuals,entities, etc., of a supply or value chain relating to a message, e.g.an inquiry, issue, idea, etc., without sacrificing knowledge of thecredibility or reliability of the information/response to the message.Existing e-mail platforms, project management systems, collaborationcommunity web applications, ticketing systems, and SRM systems fail toprovide an adequate solution.

The growing need for an environment where collaborators can shareinformation and work without knowing each other's identity orcontributions was already recognized in July 1994 in the article“Anonymous Collaboration: An Alternative Technique for Working Together”from author Andrew Lee. This article was published in SIGCHI Bulletin,Volume 26, Number 3, pages 40-46. Besides recognizing the problem andneed for such environment, Andrew Lee also describes an ANOC (AnonymousCollaboration) based software tool that supports non real-timeelectronic discussion (page 43) and group authoring (page 45), but thedescribed software rather implements a bulletin board wherein allcontributors remain anonymous. This, downgrades thecredibility/reliability of the information. In many cases, such as forinstance the question if a plastic toy contains potentially harmfulplasticizers, the initiator of the question does need to receive theanswer from a named/identified supplier, not from an anonymous source.

The closest prior art solution, United States Patent Application US2011/0010425 entitled “Techniques for Enabling Anonymous InteractiveCommunication” and published on 13 Jan. 2011, describes a platformenabling two-way communication between parties wherein one party remainsanonymous. In this systems, each party or user is assigned annon-anonymous ID and an anonymous ID. A first user can issue anelectronic message or inquiry to a second user from his anonymous ID.The response from the second user addressed to the anonymous ID of thefirst user will be sent to central system that forwards the response tothe first user without disclosing the identity of the first user to thesecond user. As is indicated by paragraph [0014] of US 2011/0010425, amessage received by the second user (first tier partner) can beforwarded to a third user (second tier partner). Again, the second usercan forward the message using his anonymous ID to thereby preventdisclosing his identity.

The system known from US 2011/0010425 is designed to increaseeffectiveness of surveys or campaigns (see paragraph [0003]). Itrequires assigning to each user two IDs upon registration: anon-anonymous ID and an anonymous ID. Each user can control concealmentof his own identity by using his anonymous ID when sending/forwarding amessage but it is not possible to conveniently control hiding theidentities of other partners when forwarding messages or sub-messagesacross several tiers of the value chain. In other words, a companycannot hide the identities of its distributors when consulting itssuppliers, unless these distributors have taken preventive actions toavoid disclosing their identities. The platform of US 2011/0010425 alsodoes not enable to invite new, external partners to contribute, and itdoes not maintain a link between the initial message and forwardedmessages/sub-messages. The system relies on the non-anonymous IDs andanonymous IDs of users to ripple back the responses to the initiator.

It is an objective of the present invention to disclose a platform andmethod for enabling anonymous collaboration between partners in a valuechain that overcomes the above mentioned shortcomings of existingsolutions. More particularly, it is an objective to disclose acollaboration platform and method that enable optionallyanonymous/confidential collaboration between different partners of asupply or value chain without sacrificing the credibility or reliabilityof the information shared. It is a further objective to disclose suchplatform and method wherein a partner can conveniently create a messageor sub-message and invite second level partners, not directly known byor linked to the initiator, to contribute thereby respecting the desireto hide the identities of certain partners when transferringmessages/responses across different levels in the value chain. Thepresent invention is directed towards technical solutions that addressthis and other needs, in addition to having other desirablecharacteristics that will be appreciated by one of skill in the art uponreading the present specification.

SUMMARY OF THE INVENTION

According to the present invention, the above defined objectives arerealized by a computer-implemented collaboration platform as defined byclaim 1, the platform comprising:

-   -   means enabling an initiator to create a message;    -   means enabling the initiator to invite a group of first degree        partners to respond to the message;    -   means enabling a first degree partner of the group of first        degree partners to create a sub-message;    -   means adapted to automatically create a link between the        sub-message and the message, or between the first degree partner        and the initiator, or between collaboration spaces established        for the sub-message and the message; and    -   means enabling the first degree partner to invite a group of        second degree partners to respond to the sub-message while        concealing identities of one or more first degree partner for        the group of second degree partners, and/or vice versa        concealing identities of one or more second degree partner for        the group of first degree partners.

Thus, the platform according to the invention provides an interfaceenabling a user, named the initiator, to create message and transmitthis message to a group of known first degree partners. It is noticedthat such group can consists of one or plural first degree partners. Themessage can contain an idea, request, inquiry, statement, table, list orother structured information and typically requires a response that willresult from collaboration. The structured information could be quitecomplex, like for instance an xml file defining the chemicalcharacteristics of a product or the life cycle assessment data of aproduct or process. Collaboration for completing/reviewing/amending thexml file may for example be requested. A first degree partner thatreceives the message from the initiator can create a sub-message that isautomatically linked through the platform with the initial message whereit is derived from. Technically, the message is copied into thesub-message, and a link is kept between the sub-message and the messageout of which the sub-message was created, or between the partnersexchanging the message, or between the collaboration spaces establishedfor the message and sub-message. The link between message andsub-message (or between partners or collaboration spaces) may forinstance be maintained in a relational database or any other databasesystem that forms part of the platform. The sub-message can be an exactcopy of the message or a modified version, e.g. a selection ofinformation, an amended version, a complemented version, a partialinquiry, etc. The owner of the sub-message is the first degree partnerwho created it. The sub-message is forwarded to second degree partners,typically not known by the initiator and not known by the other firstdegree partners. Again, the group of second degree partners can consistsof one or plural second degree partners. The first degree partnercreating the sub-message has the ability through his interface to theplatform to conceal the identities of the initiator and one or moreother first degree partners. Vice versa, the first degree partnercreating the sub-message has the ability to conceal the identities ofsecond degree partners for first degree partners. This way, businessrelations in the value chain can be protected: a product developer forinstance may not want to reveal the identity of its suppliers to theclient and it may not want to reveal the identity of its clients to thesuppliers. The first degree partner however cannot conceal his ownidentity since he represents the point of trust and guarantee forcredibility when inviting second level partners. The initial message,sub-messages and responses are all linked through the databasemaintained centrally. Each partner has the ability to consult histrusted/reliable network of further degree partners in the value chainbut does not have to disclose the identities of the consulted partners.This way, the reliability and credibility of the collected informationremains intact while the platform offers partners in the value chain thepossibility to collaborate without disclosing core knowledge such as theidentities of partners in other tiers of the value chain.

It is noticed that the first degree partner obviously acts as initiatorfor the sub-message he created. This sub-message can similarly beforwarded by a second degree partner who can invite further degreepartners in the value chain to collaborate. This way, collaborationusing the platform according to the present invention shall typicallyresult in a chain of messages, sub-messages and responses that areautomatically linked and able to be consolidated into a response for theinitiator to the initial message. Identities can be concealed incross-level transfers along the value chain, whilst each contributorstill feeds back his response to a known partner thereby guaranteeingthat reliable and credible information is collected.

According to a further aspect of the computer-implemented collaborationplatform according to the current invention, defined by claim 2, theinitiator, the first degree partners and the second degree partners arepartners of a value chain.

Indeed, although the platform according to the invention is useful inany situation or environment where partners must collaborate withoutdisclosing each others identities and/or where collaboration needs to beorganized by self-directive teams who decide independently whom toinvite to solve a problem, the invention is in particular advantageouswhen used for collaboration between partners in a business value chain,e.g. a supply chain. This is so because the entities in such supplychain consider knowledge of the identities of their respective partnersas a key asset. They prefer not to share this information with otherpartners whereas they may wish to involve these partners in thecollaboration in order to resolve an issue. When used for collaborationbetween partners in a business value chain, the current invention shallaccelerate innovation of products and services. Whereas informationexchange across companies in the value chain is a bottleneck today, thecurrent invention shall enable companies to collaborate faster andeasier.

It is noticed that partners in the context of the current invention mustbe interpreted broadly, covering e.g. business partners, stakeholders,consumers and customers, researchers or designers participating in thedevelopment of a product, NGO's or interest groups that have concernsabout a product or company, sector organizations, etc. The value chainis in this context broader than only those entities or individuals whotouch the product during production.

According to a further aspect of the computer-implemented collaborationplatform according to the current invention, defined by claim 3, thesub-message is either:

-   -   a copy of the message;    -   a copy of part of the message;    -   a modified copy of the message;    -   a modified copy of part of the message; or    -   a related message.

Indeed, a first degree partner receiving a message from the initiator,may forward this message in unmodified version or modified version to anumber of second degree partners that he likes to involve in thecollaboration. The message may be forwarded entirely or only part of themessage may be copied into the sub-message. The platform this way allowsa partner to split a message into different related sub-messages and toforward these sub-messages to different groups of second level partners.The sub-message may also be a related message. The question if a dollcontains a harmful plasticizer may for instance lead to a sub-messagerequesting information on the recipe for manufacturing the hair of thedoll. Such related message is no longer a modified copy of the initialmessage but still a question that is originated by/derived from theinitial message.

Optionally, as defined by claim 4, the computer-implementedcollaboration platform according to the current invention may comprise:

-   -   means enabling the initiator to add attributes to the message.

By adding attributes to a message, the goals and boundaries of themessages worked on by several teams or groups along the value chainremain clear even when the identities of the teams or partners in theteams are not known to the initiator. As a consequence, everyone, evenseveral degrees separated from the initiator, shall remain focused onthe goal and stay aware of critical information that is communicatedthrough the attributes of a message.

In one embodiment, defined by claim 5, the attributes may comprise a duedate for responding to the message.

The due date is the date by which the initiator expects or needs aresponse. The due date will be copied automatically whenever a linkedsub-message is forwarded to a new team or group of further levelpartners. The partner creating the sub-message however can modify thedue date, e.g. select an earlier date in case time is needed to returnthe response to the initiator once the second degree partners or thirddegree partners have responded.

In another embodiment, defined by claim 6, the attributes may comprise alegal context for the message.

Issues or messages that require collaboration may have a legaldimension. In such case it may be important that second degree partners,third degree partners, etc. are made aware of the legislation andeventual compulsory date resulting from such legislation.Advantageously, messages that have such legally compulsory due date willhave this explicitly mentioned in an attribute in such a manner thatsecond degree partners, third degree partners, etc. understand theurgency and legal requirement to respond.

In yet another embodiment, defined by claim 7, the attributes maycomprise a business context for the message.

Indeed, when individuals or entities that have to respond to a messagedo not have direct contact with the initiator of the message, there is arisk that their interpretation or perspective is different from theinitiator's as a result of which they may respond in a way that is nothelpful or even misleading. By adding a business context to the messageand by default copying the business context into correspondingattributes of sub-messages that are linked with the message, the riskfor misinterpretation and consequently the efficiency in collaboratingthrough the platform according to the invention is further improved.Business context in relation to the current invention must beinterpreted broadly, covering for instance also certain expertise. Forinstance, the business context may reveal how the impact of a product onhealth must be calculated in order to assist a supplier in makingcorrect calculations.

It is noticed that although the attributes of a due date, legal contextand business context are mentioned here above to form part of differentembodiments, any skilled person will understand that two or more ofthese attributes may be combined into a single embodiment of theplatform according to the invention. Obviously, the list of attributesthat may be added to a message is also not necessarily limited to theexamples given here above.

According to a further optional aspect defined by claim 8, thecomputer-implemented collaboration platform according the currentinvention may comprise:

-   -   means enabling an initiator to create a list of messages        containing the message; and    -   means enabling the initiator to invite a group of first degree        partners to respond to the list of messages.

Thus, the platform according to the invention also enables teams tocollaborate on a list of messages, e.g. a list of ideas, a list ofquestions, a project consisting of a list of issues, questions, tasks,ideas, etc. An initiator can create lists of messages, and partners canforward the entire lists and invite other teams to work on the entirelists. A partner can also forward one message out of a list and invite ateam or group of second degree partners to collaborate on it. A partnercan also create a new list out of one message. A message or inquiry mayfor instance lead to a list of sub-questions and tasks. A partner canalso take a sub-list of messages, create therewith a new list and invitea team of second degree partners to work on the new list.

According to a further aspect of the computer-implemented collaborationplatform according to the current invention, defined by claim 9, theplatform comprises:

-   -   means enabling the second degree partners to respond to the        sub-message.

Indeed, the second degree partners that are invited by a first degreepartner to collaborate on a sub-message will have an interface to theplatform that enables them to respond to the received sub-message. Theirresponse will also be linked automatically and centrally to thesub-message and consequently also to the initial message, such that thefirst degree partner that created the sub-message can easily integratethe response received from the second degree partner in the response tothe initiator.

According to yet another aspect of the invention defined by claim 10,the computer-implemented collaboration platform according to theinvention further comprises:

-   -   means enabling the first degree partner to respond to the        message thereby integrating one or more response received from        one or more second degree partner to one or more sub-message        linked to the message, while concealing identities of one or        more second degree partner.

Thus, when receiving responses from second degree partners andintegrating these responses in a final response to the initial messageof the initiator, the first degree partner shall respect the anonymityof the contributing second degree partners and conceal the identitiesthereof.

Optionally, as defined by claim 11, the computer-implementedcollaboration platform according to the current invention may furthercomprise a client work module comprising:

-   -   graphical user interface elements adapted to present options on        inbound messages;    -   graphical user interface elements adapted to present options on        outbound messages;    -   graphical user interface elements adapted to present options on        inbound responses; and    -   graphical user interface elements adapted to compose an outbound        response.

Thus, the client work area where users of the platform manage themessages and lists they are working on, are arranged in such a mannerthat when a response to a message or sub-message is available to theuser, the related message or sub-message where the response is linked towill automatically appear on the user's screen. At the same time, theplatform presents options on the received response or message.

As defined by claim 12 the options presented by the platform accordingto the current invention on inbound responses may comprise:

-   -   copying the inbound response to an outbound response; and/or    -   modifying and copying the inbound response to an outbound        response; and/or    -   editing or creating an outbound response with the use of a        related inbound response in a side-by-side window.

Thus, the options presented to the user receiving a response to amessage from a contributing partner can include copying the response asis into a response to the linked message and sending it in the valuechain in the direction of the originating message. Another optionpresented to the user receiving a response to a sub-message could beamending and copying the response into a response to the linked message,and forwarding that response up in the value chain towards the initiatorof the message.

Also optionally, as defined by claim 13, the computer-implementedcollaboration platform according to the current invention may comprise aclient library module comprising:

-   -   means adapted to store a user-specific history of inbound and        outbound messages and responses.

This way, users of the platform will have access to their own library ofpreviously responded messages, previously submitted responses, andeventually also information they can upload. While preparing a responseto a message, users will be able to search through previous messages andresponses. Through the library, users will also be given the opportunityto upload structured information, like for instance a bill of materialof a product, in order to be able to easily respond to certain expectedquestions like a request to specify how much of a particular substanceis present in a product. Such information would for instance be loadedfrom a structured file that contains product numbers, part numbers,their components and ingredients, the weight percentage of thesecomponents, etc. A further public library could—as a non-limitativeexample—contain all chemicals covered by REACH, RoHS, Electronic Waste,FDA or other directives, and their characteristics.

In addition to a platform as defined by claim 1, the current inventionalso relates to a corresponding method for anonymous collaboration asdefined by claim 14, the method comprising the steps of:

-   -   creating a message by an initiator;    -   the initiator inviting a group of first degree partners to        respond to the message;    -   a first degree partner of the group of first degree partners        creating a sub-message;    -   automatically creating a link between the sub-message and the        message, or between the first degree partner and the initiator,        or between collaboration spaces established for the sub-message        and the message; and    -   the first degree partner inviting a group of second degree        partners to respond to the sub-message while concealing        identities of one or more first degree partner for the group of        second degree partners, and/or vice versa concealing identities        of one or more second degree partner for the group of first        degree partners.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram illustrating an example system forimplementing one or more of the functions and features of embodiments ofthe collaboration platform according to the present invention;

FIG. 2A is a flow chart depicting exemplary methods for creatingmessages according to aspects of the present invention;

FIG. 2B is a flow chart depicting exemplary methods for creatingsub-messages according to aspects of the present invention;

FIG. 3 is a diagrammatic illustration of various example permissionsaccording to one aspect of the present invention;

FIG. 4 is a diagrammatic illustration of a collaboration space andexample features and interaction enabled thereby, according to aspectsof the present invention;

FIG. 5 is a flow chart depicting an exemplary method for invitingadditional users to access a message or sub-message, according toaspects of the present invention;

FIG. 6 is a diagrammatic illustration of a message and threesub-messages, each of which is accessible to a respective initiator andmembers/partners of an invited user group, according to aspects of thepresent invention;

FIG. 7 is a flow chart depicting an exemplary method for providing andtransmitting responses among users, according to aspects of the presentinvention;

FIG. 8A is a diagrammatic illustration of a message and fivesub-messages thereof, each of which is accessible to a respectiveinitiator and members of an invited user group, according to aspects ofthe present invention;

FIG. 8B is a diagrammatic illustration of a plurality of messages andsub-messages derived thereof, each of which is accessible to arespective initiator and members of an invited user group, according toaspects of the present invention;

FIG. 9A is a diagrammatic illustration of exemplary interaction betweenusers, the platform, and databases, according to embodiments of thepresent invention;

FIG. 9B is a diagrammatic illustration of an example database structurefor storing data according to one aspect of the present invention;

FIG. 10A is a diagrammatic illustration of an example computingenvironment for implementing the platform of FIG. 1, according to one ormore embodiments of the present invention;

FIG. 10B is a diagrammatic illustration of an example data model forimplementing the database 107 in the platform of FIG. 1, according toone or more embodiments of the present invention;

FIG. 11 illustrates a first instantiation of the collaboration methodaccording to the present invention;

FIG. 12 illustrates a second instantiation of the collaboration methodaccording to the present invention; and

FIG. 13A-13I illustrate a scenario wherein the platform and method forcollaboration according to the current invention are exploited toresolve a customer initiated question concerning the use of chemicalsubstances in a pencil with eraser; and

FIG. 14A-14C illustrate the work area or graphical user interface atdifferent instances in the scenario illustrated by FIG. 13A-13I.

DETAILED DESCRIPTION OF EMBODIMENT(S)

An illustrative embodiment of the present invention relates to acomputer implemented platform and associated method for enablinganonymous and/or confidential collaboration of individuals, experts,companies, partners, or the like, operating at multiple points along oneor more supply or value chains. In particular, the platform and methoddisclosed herein provide a collaboration environment within which agroup of invited value chain partners may interact, exchangeinformation, and add contributions to solve a user-defined problem, ormore generally, to address a message containing an idea, inquiry,structured information, etc. The partners invited to collaborate withina group may be given one or more permissions that enable or deny certainactions or information within the collaboration space, and which furthercontrol the access by each user to the message. In accordance with anexample implementation of the present invention, the invited partnersare anticipated to be members of a supply or value chain.

In particular, each partner that is invited to access the message can beenabled to anonymously (or not) create a new version of the message, aso-called sub-message. In creating such a new version, the platformautomatically generates a new collaboration space, which can bemaintained hidden and confidential from the partners of the initialgroup that was invited to collaborate on the initial message, if sodesired. A partner that creates a new collaboration space is enabled toinvite additional, second-level partners to access the sub-messagethrough the collaboration space. For example, business partners furtherdown the supply or value chain can be invited in order to provideadditional input on inquiry sub-problem or sub-inquiry that is split offinto the sub-message, while enabling the identity of these businesspartners to be concealed from the initial group of invited first-levelpartners, and vice versa. In each instance of a new version beingcreated, the platform enables the new version to be either visible to orconcealed from the members of the previous group.

As will be described in greater detail herein, a new version of amessage or so called “sub-message” can include a sub-set of the messageor a list of sub-messages that are related in some way to the message.For example, if an original inquiry from a distributor to a manufacturerof toys contains the question “Does a plastic doll contain harmfulcomponents?”, then the manufacturer of the doll can be enabled to splitthe original inquiry into two related inquiries by creating twosub-messages. One sub-message can pose the following question to thesupplier of the doll's hair: “Does hair of a plastic doll contain aharmful plasticizers or other harmful components?”. A second sub-messagecan pose the following question to the supplier of the resins for theplastic used to construct the doll: “Do resins used in a plastic dollcontain harmful plasticizers?”. Each sub-message will be considered byits receivers invited to contribute as a new message that can be furthersplit or forwarded anonymously to second level groups or teams that areinvited to contribute.

FIGS. 1 through 10, wherein like parts are designated by like referencenumerals throughout, illustrate example embodiments of the platform andmethod for anonymous and/or confidential collaboration along supply orvalue chains, according to the present invention. Although the presentinvention will be described with reference to the example embodimentsillustrated in the figures, it should be understood that manyalternative forms can embody the present invention. For example, whileexample embodiments of the present invention are described herein withreference to partners interacting at various points of supply or valuechains, it can be appreciated that such contexts, industries, or typesof groups do not limit the present invention. As just one example, thesystems and methods provided herein can allow customers or consumers ofa business to generate inquiries. As yet further possibilities,stakeholders in a company can be allowed to utilize the system describedherein to generate messages triggering collaboration with respect to newinnovations. One of ordinary skill in the art will appreciate differentways to alter the parameters of the embodiments disclosed, such as theparticular arrangement and implementation of software modules by variouscomputing environments, as well as other readily appreciatedmodifications, in a manner still in keeping equivalency with the presentinvention as defined by the appended claims.

FIG. 1 depicts an example platform 100 that can be implemented by anumber of suitable computing environments, i.e. a combination ofhardware and software, for enabling the collaboration of one or moreusers, i.e. partners in a value chain, in accordance with the presentinvention. In particular, the example platform 100 includes a clientcommunications module 102, which can connect to a communications network104, thereby enabling one or more users operating a user device 106,e.g. a workstation, personal computer, cellular telephone/device,laptop, smartphone, tablet PC, etc., to interact with and engage thefunctionality of the platform 100. It is noticed that the platformaccording to the current invention may also interact with otherapplications in the user's domain, e.g. the user's Enterprise ResourcePlanning (ERP), Product Lifecycle Management (PLM) or CustomerRelationship Management (CRM) applications running on the user's device106. As is indicated by the databases 109, the platform according to thepresent invention may also interact with other applications in thecloud, e.g. Life Cycle Assessment (LCA) databases, Google docs, GoogleSketch, Google+, Skype, Facebook, etc. More specifically, the clientcommunications module 102 can include a graphical user interface (GUI)generator 108, which can generate one or more GUIs comprising variousdisplays of information. The platform 100 optionally can include one ormore databases 107 in communication with the client communicationsmodule 102, the GUI generator 108, and/or the collaboration module 110.The databases 107 can store information and data managed and provided bythe platform 100, as described in detail herein. Alternatively oradditionally, the platform 100 can communicate through thecommunications network 104 with one or more databases 109 stored in thecloud, e.g., hosted or otherwise provided by a cloud storage provider.

The system 100 additionally includes a collaboration module 110,typically in communication with the client communications module 102,for enabling optionally anonymous collaboration between various groupsof users, e.g. groups along different tiers of the supply or valuechain. As a brief introduction, and as further described in detailherein, the collaboration module 110 can allow any of the followingactions, in addition to other capabilities: (1) creating collaborationspaces; (2) creating messages; (3) creating concealed or visiblesub-messages; (4) generating a link between a sub-message and either theoriginal message or the existing sub-message from which the newsub-message was created; (5) sending access invitations that enable auser to access the message or sub-message via the collaboration space;(6) setting and changing one or more permissions of partners invited toaccess version message or sub-message thereof; (7) enabling usersaccessing a message or sub-message to post communication to acollaboration space; and (8) enabling responses to messages to be sent.

The user devices 106 can include any number of devices. As non-limitingexamples, the user devices 106 can comprise one or more of thefollowing: a laptop, a desktop, a hand-held device, a mobile device, asmart phone, a tablet computer, a portable transceiver, a set-top box,e.g. for internet TV, and any other suitable device as would beunderstood by those of skill in the art. As such, some or all of thefeatures, components, and functions of the system 100, including theparticular implementation of the collaboration spaces, can be customizedto accommodate different and/or multiple types of devices 106 with whichthe platform 100 communicates. Furthermore, the platform 100 can beconfigured to interface with one or more other computing systems, socialmedia websites, servers, and the like, to provide users with thecapability to utilize the graphical user interfaces and collaborationspaces described herein to access various proprietary softwareapplications, various plug-ins, various social media features, or anyother tools, software, apps, information, databases, or data that is notentirely hosted by the platform 100.

For purposes of illustration, the example platform 100 is simplified anddepicts the various modules and components as discrete functionalblocks. However, one of skill in the art can appreciate that inactuality the lines of the modules and other components of FIG. 1 maynot always be well defined. Rather, the modules and components can actas a unit in many instances. Accordingly, one of skill in the art willappreciate a number of ways to merge together or split apart the modulesand components of FIG. 1, depending on the intended applications and theparticular computing environment. Furthermore, in some embodiments, amodule or component represented by only one block actually isimplemented with multiple such modules or components. Additionally,components depicted as being contained within the platform 100 can beexcluded from the platform 100, and components depicted as beingexcluded from the platform 100 can be incorporated into the platform100. One of skill in the art will readily appreciate a variety of waysto expand, reduce, or alter the example platform 100. All suchalterations and embodiments are considered equivalent variants of thepresent invention.

In general, the platform 100 enables collaboration among partners oninquiry message, via a collaboration space. The content of a message canbe any question, inquiry, issue, idea, challenge, objective, or thelike. In the context of a supply or value chain, the content of amessage can be a particular problem on which a merchant user is seekinga solution. As one example, a donut manufacturer may be interested indetermining how to manufacture gluten-free donuts. In general, themessage can have virtually any format. For example, the message can be amedia file, a document, a web page, data embedded in or presented by aweb page, information in any form, or the like. For example, messagescan be interactive or modifiable files, e.g. a fillable pdf file, and/orcan contain one or more selectable fields/buttons, e.g. as a multiplechoice question format. One of skill in the art will appreciate a broadrange of ways to implement and format the messages described herein.

FIG. 2A and FIG. 2B depict example methods by which the platform 100creates and controls access to respectively messages and sub-messages,and associated collaboration spaces. Each collaboration space isassociated with a creating user, called the initiator, and either amessage (FIG. 2A) or a sub-message (FIG. 2B). In general, sub-messageseither are created from an initial message, or they are created from anexisting or preceding sub-message. Thus, “sub-messages” as referred toherein generally can refer to messages derived from an initial message,messages derived from preceding sub-messages, and combinations thereof.As an example, supply chains in automotive manufacturing could easily byeight levels deep. In such a value chain, it could happen that overeight levels of sub-messages are generated if for instance an end-useror distributor initiates a message whose response ultimately requirescollaboration of a supplier of a small part.

The client communications module 102 can receive a request from aninitiator to create a message and associated collaboration space (step112). The request can be transmitted from the initiator's user device106 across the communications network 104 and can include informationentered by the initiator into a GUI hosted by, embedded in, or otherwiseprovided by one or more web pages and generated by the GUI generator108. In some embodiments, the message request (and resulting message)can include one or more predefined text or other types of fields orattributes containing information submitted by the initiator. Forexample, in such embodiments, the attribute fields can include any oneor more of the following: a description field, a context field, a legalrequirement field, a business requirement field, and a deadline field.Additionally or alternatively, a message can include a suggestedresponse format containing one or more pre-defined fields, such as textfields, date fields, numeric fields, unit of measurement fields, tables,and the like.

Upon receipt of the message request, the collaboration module 110 cangenerate a collaboration space and create the message in thecollaboration space from information contained in the message request(step 114). In accordance with embodiments of the present invention, thecollaboration spaces described herein can be implemented in a number ofways. For example, the collaboration spaces can each comprise one ormore web pages containing one or more GUIs generated by the GUIgenerator 108 that enable the interaction and various other featuresdescribed herein. The web pages furthermore can be in communication withone or more databases containing the data, e.g. inquiries, versions ofinquiries, assigned user permissions, chat records, discussion boardposts, social media or public web pages where consumer can post feedbackor question pertaining to a product etc., pertaining to thecollaboration space. In some further embodiments, each collaborationspace comprises at least one user-personalized web page per user withaccess to the message. Accordingly, the collaboration space need not beimplemented in a manner that presents information associated therewithidentically for each user. In fact, in some embodiments, a single webpage can provide users with information pertaining to multiplecollaboration spaces of which the user is a member.

For instance, collaboration spaces are implemented in the followingmanner in one example embodiment. When a user requests a certaincollaboration space, e.g. by selecting it, in order to view details,communications, and/or work associated with the collaboration space, theplatform 100 can automatically present the requested collaboration spacein conjunction with other related collaboration spaces that pertain tothe same message and of which the requesting user is a member.Alternatively, the platform 100 can automatically present or display asubset of the information/data associated with the related collaborationspaces pertaining to the same message. For example, the platform 100 canpresent only the message/sub-message to which the user has access.Displays or presentation layouts according to such embodiments canprovide users with convenient access to all information pertaining to asingle message (which the user is permitted to access), thereby allowingusers to easily synthesize information from multiple collaborationspaces and provide their contributions to the message.

Additionally or alternatively, the collaboration spaces can beworkspaces corresponding to a defined directory and/or filestructure/location. Such workspaces can be real or virtual, e.g.implemented by the appropriate databases and storage devices on a serveror networked through a communications device, as would be appreciated byone of skill in the art and described further herein. Furthermore, oneof skill in the art will recognize that these examples in no way limitthe present invention to the particular implementations of collaborationspaces described herein. Rather, one of skill will appreciate otherforms, database structures, and implementations that representequivalents of the present invention.

With further reference to FIG. 2A, the collaboration module 110 canassign ownership and/or one or more permissions (step 116). Inillustrative embodiments, messages are implemented as documents, freetext, or other data to which an owner may be assigned. In suchillustrative embodiments, ownership of a message is automaticallyassigned to the creating user, the initiator, such that the creatinguser is provided with a set of automatically generated permissionsenabling access to the message. In alternative embodiments, ownership ofa message can be assigned to an administrative user or to another user.Additionally or alternatively to assigning an ownership, the system 100may assign one or more permissions to the creating user that enable thecreating user with particular access rights, including the right to setpermissions of other users.

In general, when setting the permissions of users that are invited toaccess a message (FIG. 2A) or a sub-message (FIG. 2B), the platform 100can be configured to enable different access rights to be assigned todifferent members of an invited user group. For example, a userdesignated an “expert” may be assigned different access rights from abusiness partner, e.g. a supplier. For instance, the platform 100 can beconfigured to assign (either automatically or in response to a requestby a creating user) different access rights to experts, enabling expertsto view only a subset of a message or sub-message. This can bebeneficial in situations where a message or sub-message containsconfidential information that may be shared with a business partner butnot with a third-party expert enlisted simply to offer scientific orother expert opinion. Furthermore, permissions can provide different orthe same access rights to partners occupying different points along asupply or value chain. Thus, while some embodiments may provide one ormore predetermined permissions to a partner based on the partner's pointor position along a supply or value chain, such a system for assigningpermissions is not required. Accordingly, the present invention is notlimited to any particular system or mechanism for determiningpermissions, and is not limited as such to platforms featuring amechanism for setting permissions.

Some embodiments according to present invention provide the creatinguser the ability to submit, e.g. as a part of the message request, thenames, contact information, etc. of one or more users/partners to beinvited using the platform 100 to access the message. In general,permissions of users invited to access the message may be assignedautomatically, based on information contained in the message request, orbased on some combination thereof. For example, the initiator of themessage may be allowed to additionally select and submit one or moreparticular permissions for each partner that the initiator includes inthe invitation list, thereby controlling access of the invited partnersto the message.

In embodiments where the user is given the option to submit aninvitation list comprising one or more partners to be invited to accessthe message, the creation of the collaboration space can additionallyinclude sending an invitation to the one or more partners included inthe invitation list (step 118). One of skill in the art will appreciatethat depending on the embodiment and implementation, the steps depictedin FIG. 2A and subsequent Figures need not be executed in the specificorder that is shown, unless otherwise noted. For example, it may bepossible for the steps to be rearranged in a different order or fornumerous steps to occur simultaneously.

As is illustrated by FIG. 2B, the client communications module 102 canalso receive a request from the receiver of a message, i.e. a so calledfirst degree partner invited to collaborate on a message, to create asub-message and associated collaboration space (step 120). Upon receiptof the sub-message request, the collaboration module 110 can thengenerate a new collaboration space and create the sub-message in the newcollaboration space from information contained in the sub-messagerequest (step 122). With further reference to FIG. 2B, the collaborationmodule 110 can assign ownership and/or one or more permissions to thesub-message (step 124). In embodiments where the first degree partnerthat requests creation of a sub-message is given the option to submit aninvitation list comprising one or more second degree partners to beinvited to access the sub-message, the creation of the new collaborationspace can additionally include sending an invitation to the one or moresecond degree partners included in the invitation list (step 126). Thesteps depicted in FIG. 2B will be described in more detail furtherbelow.

FIG. 3 depicts further illustrative examples of the permissions 128assigned by the collaboration module 110. In particular, the permissionscan include any one or more of the following: permission(s) to read themessage 128 a, permission(s) to modify the message 128 b, permission(s)to request the creating user to send an invitation to access the message128 c, permission(s) to initiate the system 100 to send accessinvitation(s) 128 d, permission(s) to create sub-messages 128 e,permission(s) to submit a response to the message 128 f, andpermission(s) to participate in particular communication mechanismsenabled or supported by the collaboration space 128 g. One of skill inthe art can appreciate that many other permissions and access rights arepossible and contemplated within the scope of the present invention.

Generally, the collaboration space can facilitate a wide variety ofinteractions between the creating user and the invited users. Forinstance, FIG. 4 schematically depicts several illustrative examples ofsuch interactions. An example collaboration space 130, diagrammaticallydepicted as a circle, includes an example message 136 created by anexample creating user 132, designated schematically by a star. Inaddition to the creating user 132, the message 136 is accessible byseven example invited users 134. The specific access rights of each userare determined by one or more specific permissions 128. While thepermissions 128 are illustrated as a simple lock in FIG. 4, one of skillin the art can appreciate that each user can be assigned a set of one ormore permissions, which can, for example, be specific to any number orplurality of different applications, software, functionality, etc.

Furthermore, via the collaboration space 130, the creating user 132and/or the invited users 134 can be enabled to launch plug-ins, runsoftware/applications, including potentially proprietary and/or licensedsoftware, and access communication features or modules generallysupported by, accessible through, and/or otherwise provided by thecollaboration space and one or more GUIs generated by the GUI generator108. For example, users can be allowed or enabled to utilize socialmedia forms of communication, video conferencing 401, blogging, “livetalk” features 402, discussion boards 403, chat rooms 404, instantmessaging, file uploading 405, and many other features. One of skill inthe art will appreciate that the specific examples of FIG. 4 are in noway limiting, but rather are provided for purposes of illustration.

Furthermore, any or all of the discussions boards, chats, chathistories, uploaded files, and any or all other communications enabledby the collaboration space 130 can be kept hidden and confidential fromusers without the requisite permissions to access the collaborationspace 130 and/or the message 136. In general, user permissions can beset that enable or deny the ability to access, e.g. view, modify,create, etc., communications enabled by the collaboration space 130. Asone example, permissions can be set in such a way so as to provide (1)the creating user 132 and all invited users 134 with full access rightsto all or some of the communication features or modules in thecollaboration space 130, and (2) one or more other users not invited tothe collaboration space 130 with partial access rights, e.g., read-only,to all or some of the communication features or modules in thecollaboration space 130. As an alternative example, permissions ofinvited users 134 to access all or some of the communication features ormodules in the collaboration space 130 can be set by the creating user132. For example, the creating user 132 can be provided with thecapability to individually set each invited user 134's access rights toeach of the communication features or modules in the collaboration space130.

For instance, the creating user 132 may determine that a first inviteduser is permitted to participate in only discussion boards and chatrooms, that a second invited user is permitted to participate in onlyuploading files and video conferencing, that a third invited user ispermitted to participate in all communication features and modules inthe collaboration space 130, etc. In this manner, embodiments of thepresent invention can enable the communications of each of a pluralityof collaboration spaces, such as the example collaboration space 130, tobe fully or partially confidential, e.g. as desired by the creating userof each collaboration space. Another example could be that the initiatorcan prevent a participant to access a document as long as theparticipant does not accept a non-disclosure agreement (NDA). Access toa document could also be restricted by the platform as long as theparticipant does not accept an NDA that is required by the owner of thedocument. In such case, the owner may not necessarily be part of thecurrent workspace. The document for instance could have been copied froma related message if the workspace deals with a sub-message.

Additionally, once a collaboration space is created, the creating usermay send additional access invitations as desired. For example, if thecreating user is a distributor, he or she may decide to initially sendaccess invitations to two business partners who are suppliers. Uponholding two video conferences and exchanging several messages, the threeusers accessing the collaboration space may determine that expertopinion regarding the message is required in order to make additionalprogress toward a solution or response. In such instances, the creatinguser, i.e. the distributor in the example, may invite an expert as afourth user to access the collaboration space. In a similar manner,requests for the system 100 to send invitations to access thecollaboration space can also be initiated by a user provided withpermission to send access invitations.

FIG. 5 depicts an exemplary embodiment of the system 100's response toreceiving an access request from a user. At step 138, the communicationsmodule 102 can receive a request from a user to send an accessinvitation to one or more additional users, such as an expert. In someembodiments, the user may be further allowed to submit one or morepermissions for the collaboration module 110 to assign to the user beinginvited to access the collaboration space. For example, the accessinvitation request can include one or more selectable, fillable, etc.fields for enabling the inviting user to select one or more permissionsfor the user recipients of the invitation. Alternatively oradditionally, the permissions can be automatically assigned by thesystem 100, based on a predetermined set of permissions. For example, insome embodiments, the system 100 is configured to automatically assignall users designated as experts a predetermined set of one or morepermissions.

At step 140, the collaboration module 110 can send an access invitationto the one or more invited users or partners included in the accessinvitation request. More specifically, the collaboration module 110 cancommunicate with one or more electronic mail (e-mail) servers, e-mailservices, instant messaging services, communication web pages, or thelike, in order to electronically send an invitation one or moreadditional users to access the collaboration space. The additional usersthat are invited to access the collaboration space can be users with apre-existing user account through which the functions of the system 100described herein are generally accessible. In some embodiments, userswith a pre-existing user account are enabled to view invitations at aweb page hosted by the system 100. Alternatively, the invited partnerscan be users without such a pre-existing user account. For example,users without pre-existing user accounts can be enabled to access thecollaboration space. For example, an e-mail or other message can be sentto such users without a pre-existing user account that enables the userto create such an account and thereby access the collaboration space. Asan additional non-limiting example, users without pre-existing useraccounts can be sent an e-mail or other message that contains a link toa web page providing access to the collaboration space. Upon navigatingto the web page of the link, such a user can be automatically assigned auser identification or user name with which the user will interact withthe collaboration space.

In some embodiments implemented with user accounts, users additionallycan be allowed to invite new users to create a user account, e.g. byproviding contact information such as an email address. The system 100can receive such contact information submissions, determine whether thereceived contact information has been registered with the system 100under an existing user account, and subsequently send an invitationusing the contact information inviting the user associated with thecontact information to register a new user account if not alreadyregistered. Alternatively, if the system 100 determines that thereceived contact information is already associated with an existingaccount, then the system 100 can provide the existing accountinformation to the user that initially submitted the invitation to thesystem 100.

Continuing with the method of FIG. 5, the collaboration module 110 canassign one or more permissions (step 142) controlling the access of theuser(s)/partner(s) to whom an access invitation was sent. In furtherembodiments, the one or more permissions being assigned can be selectedas described previously herein, e.g. by the system 100, by the usersending the invitation, by the creating user of the collaboration space,or by some combination thereof. The step 142 of assigning one or morepermissions can be executed prior to sending the access invitation,simultaneous with sending the access invitation, or subsequent tosending the access invitation, as would be appreciated by one of skillin the art.

In illustrative embodiments of the present invention, the identity ofthe initiator and the identity of each invited first degree partner isautomatically visible to other invited first degree partners within agiven collaboration space. In alternative embodiments, some or all ofthe identities of partners accessing a single collaboration space orinquiry can remain hidden or concealed. For example, in someembodiments, each partner that is invited to join the collaborationspace, i.e. access the inquiry, is enabled to select whether to permitor deny other invited users existing within or subsequently invited intothe collaboration space to view his/her identity.

Once an initial collaboration space is created for enabling an initialgroup of invited first degree partners to address a message, alsoreferred to as an initial invited user group, the system 100 enables thecreation of one or more additional or subsequent collaboration spaces tobe formed by members of the initial user group. In particular, eachinvited first degree partner may be assigned one or more permissionsenabling or denying him/her the ability to create a sub-message. And ina similar manner, each member of an invited user group with access to asub-message may be assigned one or more permissions enabling or denyinghim/her the ability to create a further sub-message.

Returning now to FIG. 2B, an exemplary method is depicted for creating asub-message, according to illustrative embodiments of the presentinvention. As described previously herein, members of an initial inviteduser group can be permitted either automatically, manually, or somecombination thereof, to send a request to create a sub-message, whichinitiates the system 100 to create the sub-message. Accordingly, if sucha request is submitted, then the request is received (step 120) by theclient communications module 102. The client communications module 102initiates the collaboration module 110 create a sub-message (step 122)of the inquiry and a new collaboration space through which thesub-message will be accessible, ownership and permissions to access thesub-message are set (step 124) and an invitation to access thesub-message is sent to second degree partners (step 126).

In illustrative embodiments, access to any newly created or subsequentsub-message is only initially provided to the creating user of thesub-message and any invited users initially provided by the creatinguser of the sub-message, e.g., in the request to create a sub-message orin a subsequent access invitation request from the creating user of thesub-message. In some embodiments, the subsequent creating user, i.e. theinitiator of the sub-message, is enabled to choose whether the initialcreating user, i.e. the initiator of the parent message, is to bepermitted access to the subsequent collaboration space or sub-message,e.g. by selecting a selectable field on a GUI created by the GUIgenerator 108 and presented to the user at the user device 106.Additionally or alternatively, a subsequent creating user can be enabledto choose whether or not to conceal the existence of the sub-messageand/or the identities of any members of the subsequent invited usergroup, i.e. second degree partners, to the initial creating user or tomembers of the initial invited user group, i.e. first degree partners.

In general, the functions, permissions, interactions, etc. describedwith reference to the initial collaboration space for accessing theoriginal message similarly can apply to subsequent collaboration spacesfor accessing sub-messages. However, it is not a requirement of thesystem 100 for such functions, permissions, interactions, and otherfeatures to be identical for all collaboration spaces, or even any twocollaboration spaces. As one example, permissions to sub-messages neednot be assigned in the same manner that permissions are assigned to theparent message. For instance, in some embodiments, the initiator of theparent message may be provided with the ability to assign permissionsthat specifically allow or deny each first degree partner of the initialinvited user group, i.e. each user with access to the parent message,the ability to set permissions of second degree partners, i.e. membersof subsequent invited user groups. For example, the initiator of amessage can be permitted to select which first degree partners in theinitial invited user group are allowed to create sub-messages; theinitiator of the parent message may further be permitted to select whichfirst degree partners in the initial invited user group are allowed toset the permissions of subsequent users invited to access such createdsub-messages. Very likely, default participant rights that cover 90% ofthe cases will be set. These default rights may be linked to defaultparticipant types or can be linked to types of collaboration spaces.Typical examples of collaboration spaces with appropriate rights thatfit a certain type of subject or context will be saved as templates andwill be accessible in a library or through a wizard.

Continuing with FIG. 2B, at step 124, the collaboration module 110 canassign ownership and/or permission(s) to the creating user of thesub-message and to any users provided to the system 100 in an accessinvitation request from the creating user of the sub-message. Next, atstep 126, one or more access invitations can be sent to one or moreusers if any access invitation requests were included in or with therequest to create a sub-message. Once the subsequent collaboration spaceis created to provide access to the sub-message, the new collaborationspace can enable any of the communication features and capabilitiesdescribed previously herein, such as the communication featuresdescribed with reference to FIG. 4. Similarly, invited second degreepartners with access to a sub-message can be assigned one or morepermissions enabling or denying them to create further sub-messages. Forexample, by executing steps 120 through 126, a user invited to access asub-message of a message can create a sub-message of the sub-message.

In this manner, illustrative systems and methods according the presentinvention provide the capability to generate successive sub-messages orversions of a message, as depicted schematically in FIG. 6.Specifically, FIG. 6 illustrates four example collaboration spaces 150,152, 154, and 156. Initiating partners are distinguished from invitedpartners by a star. Collaboration spaces are depicted diagrammaticallyby a ring. For example, collaboration space 150 provides an initiator158 and three invited first degree partners 160, 162, and 164 withaccess to an initial message 168. Through the system 100, invited firstdegree partner 162 created a sub-message S1 or 170 of the message 168,which is accessible through the collaboration space 152. In a similarmanner, invited first degree partner 164 created a sub-message S2 or 172of the message accessible through collaboration space 154, and invitedsecond degree partner 176 created a further sub-message S3 or 174 of thesub-message 170 accessible through collaboration space 156. Accordingly,a single user can be both an invited partner in one collaboration spaceand an initiator of a different collaboration space, as depicted by FIG.6. It is noticed that in the example of FIG. 6 as well as in FIG. 8A andFIG. 8B, the initiator of the subsequent messages is each time a memberof the collaboration space of the parent message. This is only onepossibility though. As will be illustrated by FIG. 11 and FIG. 12,described further below, the messages can also be sent to contributorssuch that a new contributor becomes initiator of a new collaborationspace, without being a member of the collaboration space of the parentmessage.

Additionally, in some embodiments, creating users of a sub-message canbe enabled to use the collaboration space to provide a response to theparent message or sub-message from which it was created. For example,the collaboration space of a sub-message can provide each creating userwith a feature for responding, e.g. a “Respond Now” button on a GUI,which, when activated, prompts the creating user to attach a file orgenerate a response, e.g. as free text, etc., for the system 100 tosend. As illustrative examples, a response can comprise any one or moreof the following: an answer, a confirmation, additional input, afollow-up question, a question requesting clarification, a reply, acomment, a selection of one or more options or selectable fields/buttonsprovided in the sub-message, and/or any other type of response.

The feature of sending a response can be enabled by creating anassociation, e.g. a link, between the sub-message and the parent messagefrom which the sub-message was created. Thus, step 122 depicted in FIG.2 can include the additional step of the system 100 automaticallycreating an association between the sub-message and its parent, e.g.either the message itself or some preceding sub-message) and causing theassociation to be stored in a database. As alternatives, however,associations between collaboration spaces can be manually established bya system administrator or a user provided the user has the appropriaterights on both the messages he wishes to link. The user may for instancebe member of the collaboration space and initiator/owner of the messagehe wishes to link to the first message. An example could be a questionwhere a plastic doll contains certain harmful substances. While theissue is being treated with several sub-messages in the supply chain, anew question may come in with almost the same content. The productmanager of the doll can then assign the question to the workspace thatis already dealing with the question. As illustrative examples, theassociation or link that is optionally created in step 122 can includeany one or more of the following: an association between the sub-messageand its parent, an association between the initiator of the sub-messageand the initiator of its parent, or an association between thecollaboration space of the sub-message and the collaboration space ofits parent.

For example, in illustrative embodiments, the association or link can beimplemented with a table data structure. For instance, the system 100can create a new table of relations for each message that is created.For any given message, the corresponding table of relations tracks theassociations between the message and its sub-messages. Thus, each time apartner creates a sub-message of an existing message, a new entry orvalue is added to the table corresponding to the existing message, andthe new entry or value represents the new sub-message that has beencreated. Additionally, each time a user creates a new message, thesystem 100 creates and stores a new table of relations for tracking theappropriate associations. As would be appreciated by one of skill in theart, the tables of relations can be stored in a local database, a remotedatabase, a cloud database, or a combination thereof. As an alternativeto the just described tables memorizing links between messages andsub-messages, the link between users or collaboration spaces may bememorized.

Each of the tables of relations further can be configured to track thepartners (and their permissions) that are associated with and haveaccess to the corresponding message and its related sub-messages.Accordingly, the tables of relations can be utilized to performfunctions associated with building or presenting collaboration spaces,including, as examples: (1) presenting related messages to a particularuser having access to the related messages; (2) sending an answer orresponse from a sub-message to its parent sub-message or message; and(3) sending certain types of automated messages, i.e., messages that donot require manual intervention by users, such as due date reminders,inquiry updates, update requests, etc. For example, the system 100 canbe configured to utilize one of tables of relations in order to send areminder received from an original creating user to all sub-messagesrelated thereto.

Using such associations, e.g. links and entries in the tables ofrelations, the system 100 enables responses to be quickly andefficiently transmitted to an initiator of a message from an invitedpartner of a sub-message who is anonymous to the initiator of themessage. Similarly, the invited partner of the sub-message further maybe unaware of the identity of the initiator of the message, thusavoiding negative impacts on the business of members of the supply orvalue chain members occupying intermediate points between that of theinvited partner of the sub-message and that of the initiator of themessage. Furthermore, such associations can enable the members ofinvited user groups along a supply or value chain of precedingsub-messages to remain anonymous (if so desired) while maintaining asystem enabling the various invited user groups to work toward asolution on a common problem.

FIG. 7 describes an exemplary method by which the platform 100 reacts tothe submission of a response. The communications module 102 receives theresponse from the initiator of a sub-message (step 144). Thecollaboration module 110 can then, in one possible implementation,utilize the link or other association created in step 122 to provide theresponse to the initiator of the parent of the sub-message (step 146).In another possible implementation, the communications module 102 wouldprompt the initiator of the sub-message in step 144 that the receivedresponse may be useful to provide a response to the parent message, andsuggest different alternatives: copy the response into a response to theparent message, copy and amend, or simply create or edit the response tothe parent message while viewing the response to the sub-message in aseparate window side-by-side. Additionally or alternatively, theresponse can be provided to any invited partners with access to theparent of the sub-message. One of skill in the art will appreciate thatthe step 146 of providing the response to the initiator of the parent ofthe sub-message can include any one or more of the following: providingthe response, providing a copy of the response, providing a link to theresponse, or the like. The response can be provided via e-mail, via thecollaboration space of the initiator of the parent, via a messagingservice, or via any other suitable communication feature. Once theresponse is accepted by the initiator of the parent message as finalresponse, the status of the message will be changed to “answered”, sothe platform stops prompting for updates and/or sending due datereminders. The status change dates will be stored so they can be usedfor status reports and statistics later on.

In a first illustrative example, the collaboration space is implementedas one or more personalized web pages. Accordingly, step 146 cancomprise including or adding the response to one or more of the webpage(s) personalized specifically for the initiator of the parentsub-message. For example, in such embodiments, the personalized webpage(s) of any initiator of a parent sub-message can be automaticallymodified by the system 100 as a result of the communications module 102receiving a response from an initiator of a sub-message of the parentsub-message. In this manner, the web pages of initiators of parentsub-messages can be automatically updated or modified to provide accessto a response submitted by the initiator of a sub-message of the parent.In a second illustrative example, the platform 100 can automaticallyemail as an attachment any received response to the initiator of aparent sub-message.

Upon the system 100 receiving a response from an initiator of asub-message (step 144), and in addition to providing the response to theinitiator of the sub-message's parent (step 146), the system 100optionally can prompt the parent user, message, or group (or acombination thereof), e.g., with an opportunity to further send alongthe received response (step 148). For example, upon receiving theresponse (step 146), the platform 100 can automatically provide theinitiator of the sub-message's parent with a graphical user interfacethat allows the initiator to initiate the platform 100 to further passalong the response unmodified or modified or incorporated into a newlycreated or edited response. In particular, if the parent is itself asub-message, then it too has a parent. In such scenarios, the system 100can automatically provide the initiator of the sub-message's parent withthe option to send the response to its parent. This is depictedschematically by the example of FIG. 8A.

FIG. 8A shows five collaboration spaces 208, 210, 212, 214, and 216,represented by straight bars. Five respective initiators 188, 190, 192,194, and 196 are depicted by a star, and any invited partner isrepresented by a circle. In the example, a message 198 was created by aninitiator 188, and successive sub-messages 200 or S1, 202 or S2, 204 orS3, and 206 or S4 of the message were created by the initiators 190,192, 194, and 196, respectively. Accordingly, if user 196 submits aresponse, e.g. on behalf of the users of collaboration space 216, thenthe response is provided in step 146 of FIG. 7 to user 194.Additionally, in step 148, user 194 can be provided the option to sendthe response to user 192, i.e. the initiator of the parent of thesub-message 204 created by user 194. If user 194 selects for theplatform 100 to provide the response to user 192, e.g. after reviewingthe response and determining that it is adequate, then the platform 100repeats step 146 and optionally step 148 of providing the response touser 192 and prompting user 192 with an option to provide the responseto user 190. Accordingly, in this manner, steps 146 and 148 can berepeated until the response is passed along from user 196 all the way upto user 188, the initiator of the inquiry itself. The process ofrepeating steps 146 and 148 thus ends at step 149 of FIG. 7, at whichthe response is provided to the initiator 188 of the message 198.

FIG. 8B demonstrates some benefits of such a system when implemented fora highly complex network of users, particularly where there may exist adesire among users to maintain anonymity. Specifically, FIG. 8B depictsa plurality of sub-messages all originating back to an initial message178 created by a user 218. Each sub-message can be categorized based onits degree of separation from the initial message 178. Accordingly, allmessages enclosed by dashed box 180 are first degree sub-messages.Similarly, dashed box 182 encloses second degree partners, dashed box184 encloses third degree partners, and dashed box 186 encloses fourthdegree partners. As an illustrative example, each dashed box representsa different point in a supply or value chain. Accordingly, using themethods described herein, such a system can quickly and efficientlytransmit information pertaining to a message through multiple points ofa complicated and crowded supply or value chain, all while enabling theidentity of each member of any invited user group to be concealed orvisible from each member of each different invited user group.

In general, any sub-message can be a modified copy or an unmodified copyof the parent message or sub-message from which it is created.Furthermore, each sub-message can contain all or a subset of theimmediately preceding data copy, i.e., the parent message orsub-message. For example, in some instances an initiator may create amessage such that it comprises a list of related messages. In suchinstances, subsequent copies of the message may include modified orunmodified subsets of the initial list. As one illustrative example,each sub-message can be implemented as a data copy of the parentmessage/sub-message from which it was created. Accordingly, the messageand related sub-messages together can form one or more data chains eachcomprising a plurality of successive data copies being joined by linksor other associations.

As would be appreciated by one of skill in the art, data comprising themessages, user permissions, communication histories between users likee.g. messages, chat histories, etc., user accounts and information, andother features of the collaboration spaces can be stored in one or moredatabases. Generally, the databases can be real or virtual, and as suchcan be stored on one or more servers, in the cloud, e.g. using uniquecloud identifications for retrieving data to create the collaborationspaces, on the individual user devices 106, and combinations thereof.One of skill in the art will appreciate that the particular manner inwhich information is stored and collected can vary depending on theparticular choice of implementation for the collaboration spaces, etc.

For example, in illustrative embodiments according to the presentinvention, the collaboration spaces are implemented through userclients, e.g. web browsers on a computing device, UI applications orapps on a smart phone device, and any other clients/devices that presentuser-personalized displays of information to each user. For instance,the user-personalized displays of information can present users withlists of messages to which they have access, wherein the list comprisesa plurality of links to additional displays each of which presents theuser with information pertaining to that particular message/sub-message,e.g. the message/sub-message, discussion boards, comment chains, chathistories, or the like. Accordingly, in such embodiments, themessage/sub-messages, discussions boards, comment chains, chathistories, etc. all can be stored in one or more central databases.Furthermore, for embodiments implemented specifically for one or moresocial media forms of communication, it may be desirable for theplatform 100 to additionally be implemented by one or more otherdatabases that are separate from the one or more central databases. Forexample, the one or more additional databases can be specificallyconfigured to store data relating to the social media communication orother features with a potential for high traffic loads.

As yet an additional example of storing data for illustrativeembodiments, data that is stored in one or more databases experiencingincreased traffic can be duplicated to a new host location with loadbalance technology. In this manner, a duplicate database can be createdfor assisting with the high-load without disrupting the work flow of theplatform 100. For example, in embodiments wherein such databases arestored in the cloud, information in a duplicate database or an originaldatabase can be easily stored, managed, and retrieved by utilizingunique cloud identifications (IDs) for storing the data in theparticular desired structured manner, e.g. assigning each user a uniquecloud ID, etc.

Accordingly, the platform 100 can be in communication with one or moredatabases. For example, the collaboration module 110 can be configuredto initiate storage actions for storing information received from theclient communications module 102 in one or more databases, such as thedatabases described previously herein. FIG. 9A depicts one example ofthe manner in which the platform 100 can store information indatabase(s) 228. An initiator creates a message (step 220), which caninitiate the platform 100 to create one or more collaboration spaces CS1that can be saved in the database(s) 228 and additionally can cause thesystem 100 to store the message in the database(s) 228. In someembodiments, and depending on the particular implementation of thecollaboration spaces, it may not be required for the platform 100 tobuild a collaboration space until a user specifically requests to accessit. Accordingly, the collaboration spaces shown in FIG. 9A are depictedfor illustration and are not required.

The initiator can invite additional users, i.e. first degree partners,to access the collaboration space CS1 (step 222). For instances orembodiments wherein the users being invited interact with the platform100 through pre-existing user accounts that are provided by the platform100, step 222 can include: (1) the first user sending an accessinvitation request to the platform 100, (2) the platform 100 providingan invitation to the invited first degree partners, e.g. by retrievingthe user accounts/contact information of the invited users and sendingan invitation, or alternatively by automatically modifying thecollaboration spaces for the invited users to provide the invited userswith an access invitation, and (3) one or more permissions controllingaccess to the message being assigned and stored in the database(s) 228.

Contributions and communications can be added to the collaboration spaceCS1 by first degree partners accessing the collaboration space CS1and/or associated message (step 224). Posts, responses, etc. can beautomatically stored by the platform 100 in the database(s) 228 oncereceived by the system 100. An invited partner with access to thecollaboration space CS1 can create a new sub-message of the message(step 226). In particular, this can comprise (1) the invited firstdegree partner sending a request to the platform 100 to create thesub-message and including one or more second degree partners to inviteto access the sub-message, (2) the platform 100 creating a collaborationspace CS2 and storing the sub-message in the database 228, (3) theplatform 100 storing an association 229 in the database(s) 228, e.g. alink) between the message and the sub-message, (4) the platform 100providing an invitation to the invited second degree partners, e.g. byretrieving the user accounts/contact information of the invited usersand sending an invitation, or alternatively by automatically modifyingthe collaboration spaces for the invited users to provide the invitedusers with an access invitation, and (5) one or more permissionscontrolling access to the sub-message being assigned and stored in thedatabase(s) 228.

In such embodiments as depicted in FIG. 9A, the database(s) 228 can beimplemented by multiple databases, as would be appreciated by one ofskill in the art. For example, FIG. 9B depicts one exemplary databasestructure for storing information associated with themessages/sub-messages, and collaboration spaces. A first database 230can be configured to store information such as messages/sub-messages232, discussions 234, other information pertaining tocommunication/interaction of users 236, associations or links 238between sub-messages and messages, and other information. A seconddatabase 240 can be configured to store information such as user accountinformation 242, registration forms 244 that enable user accounts to becreated, user relationships 246 describing the manner in which users areassociated, e.g. business partners, “User A is a supplier to User B”,etc., user organizations 248 of which users may be members, and otherinformation.

Additionally, the system 100 may include or communicate with one or moreadditional databases 250. For example, in embodiments implemented forsupply or value chain collaboration, the additional databases 250 caninclude databases stored locally on a particular user's computing deviceand containing information related to the product or service developedand/or sold by the user, the user's business, e.g. business data,financial information, balance sheets, etc., or the user's organization.Additionally or alternatively, the databases 250 can include databasescontaining public knowledge, such as legislation information pertinentto a user's business, product requirements and norms as determined bygovernmental regulation agencies, standard practices and methodologiesemployed in the business, and/or other information.

One of skill in the art will appreciate a number of ways to store andmanage the data and information described herein. All such embodimentsand implementations are contemplated within the scope of the presentinvention. Accordingly, the illustrative implementation and databasestructures/configurations of FIGS. 9A and 9B are provided for clarityand explanation. In no way do these particular illustrativeimplementations limit embodiments of the present invention.

When implemented specifically for supply or value chain contexts andusers that occupy particular points along a supply or value chain,additional features may be provided which utilize these relationships.For example, one or more user relationships, depicted as included in thesecond database 240 of FIG. 9B, can enable the platform 100 to provideusers with one or more lists of known business partners. The lists canbe categorized or classified in any number of ways, e.g. “My Suppliers”,“My Experts”, etc.). As an example of possible uses of such lists, auser's business partners can be displayed on a web page through which amessage/sub-message is accessible, e.g. a web page implementing acollaboration space of which the user is an invited member. Furthermore,these lists or individual names of users on such lists can be selectableor associated with numerous commands. For example, in one embodiment,clicking a name causes a menu to appear on the display, with variouscommand options. The command options can include, for example, a commandto send an access invitation to the selected user(s), a command torequest the initiator of the message/sub-message to send an accessinvitation to the selected user(s), a command to view/modify thepermissions of the selected user(s), a command to terminate the selecteduser's access to the message/sub-message, or the like.

FIG. 10A illustrates an example computing device 1000 within anillustrative operating environment for implementing embodiments of themethod and platform of the present invention. The computing device 1000is merely an illustrative example of a suitable computing environmentand in no way limits the scope of the present invention. A “computingdevice” as represented by FIG. 10A can include a workstation, a server,a laptop, a desktop, a hand-held device, a mobile device, a tabletcomputer, or other computing devices, as would be understood by those ofskill in the art. Given that the computing device 1000 is depicted forillustrative purposes, embodiments of the present invention may utilizeany number of computing devices 1000 in any number of different ways inorder to implement a single embodiment of the present invention.Accordingly, embodiments of the present invention are not limited to asingle computing device 1000, as would be appreciated by one with skillin the art, nor are they limited to a single type of implementation orconfiguration of the example computing device 1000.

The computing device 1000 can include a bus 1010 that can be coupled toone or more of the following illustrative components, directly orindirectly: a memory 1012, one or more processors 1014, one or morepresentation components 1016, input/output ports 1018, input/outputcomponents 1020, and a power supply 1024. One of skill in the art willappreciate that the bus 1010 can include one or more busses, such as anaddress bus, a data bus, or any combination thereof. One of skill in theart additionally will appreciate that, depending on the intendedapplications and uses of a particular embodiment, multiple of thesecomponents can be implemented by a single device. Similarly, in someinstances, a single component can be implemented by multiple devices. Assuch, FIG. 10A is merely illustrative of an exemplary computing devicethat can be used to implement one or more embodiments of the presentinvention, and in no way limits the invention.

The computing device 1000 can include or interact with a variety ofcomputer-readable media. For example, computer-readable media caninclude Random Access Memory (RAM), Read Only Memory (ROM),Electronically Erasable Programmable Read Only Memory (EEPROM), flashmemory or other memory technologies, CDROM, digital versatile disks(DVD) or other optical or holographic media, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devicesthat can be used to encode information and can be accessed by thecomputing device 1000.

The memory 1012 can include computer-storage media in the form ofvolatile and/or nonvolatile memory. The memory 1012 may be removable,non-removable, or any combination thereof. Exemplary hardware devicesare devices such as hard drives, solid-state memory, optical-discdrives, or the like. The computing device 1000 can include one or moreprocessors that read data from components such as the memory 1012, thevarious I/O components 1016, etc. Presentation component(s) 1016 presentdata indications to a user or other device. Exemplary presentationcomponents include a display device, speaker, printing component,vibrating component, etc.

The I/O ports 1018 can allow the computing device 1000 to be logicallycoupled to other devices, such as I/O components 1020. Some of the I/Ocomponents 1020 can be built into the computing device 1000. Examples ofsuch I/O components 1020 include a microphone, joystick, recordingdevice, game pad, satellite dish, scanner, printer, wireless device,networking device, or the like.

Accordingly, the collaboration platform and method provided hereinenable numerous benefits. When implemented for supply or value chains,the systems and methods can enable collaboration of members operating atmultiple points along a supply or value chain on a common inquiry.Through the platform and method described herein, a user can create amessage and invite other users to access the message. The creating useror initiator can be allowed to control the invited users' access to themessage through one or more permissions. The invited users can bepermitted to create sub-messages of the message and inviting their ownbusiness partners, etc. to access the sub-message. This enables furthercollaboration on the message at an additional step down the supply orvalue chain. For example, returning to FIG. 8B, each dashed box 180,182, 184, and 186 can generally represent different points of a supplyor value chain.

Thus, by passing along a message, i.e. creating new sub-messages, usersenlisted to collaborate with an initial creating user of the message areallowed to further collaborate with their own business partners,suppliers, etc., all in a safe manner that avoids undue exposure.Accordingly, members of an invited user group can be allowed to haveopen discussions with their business partners, etc. while concealing theidentity of their business partners as well as the content of informalbrainstorming exchanges from the initial creating user, if so desired.In this manner, a plurality of successive sub-messages can be createdenabling the anonymous and confidential collaboration of members atvarious different points of a supply or value chain.

In accordance with the present invention, and from the perspective of asingle user occupying a particular point of a supply or value chain,such a user is enabled to (1) create a message and quickly andefficiently receive responses that will aid in developing a solution tothe message, (2) draw on the knowledge of many different members atmultiple different points in the value chain, (3) allow partners invitedto access the message to maintain the anonymity of their suppliers,business partners, etc. if so desired, thereby enabling greater effortstoward developing a solution without detrimental business exposure, and(4) invite experts to weigh in on messages and provide opinions oranalysis of various aspects of a message.

FIG. 10B shows an example data model that can be used for implementingthe relational database 107 in FIG. 1. The data model shows a firstblock 1030 wherein user and account administration is maintained, asecond block 1040 wherein collaboration data are kept, a third block1050 for storage of work area queries, a fourth block 1060 whereincollaboration master and reference data are memorized, and a fifth block1070 for solution administration.

The user and account administration block 1030 has a container 1031 foruser related data like a user ID, the user's account type, the user'scontact information, the organization where a user belongs to, thepreferred language of the user, the time zone wherein the user resides,and his activity status (e.g. “online” or “offline”). For theorganizations where users belong to, container 1032 stores theorganization's ID, the organization's data (like address, predefinedworkspaces, user groups, etc.), and account particulars (e.g. the numberof users that can use the organization's account). The user and accountadministration block 1030 further hosts a user relation container 1033wherein the user ID and type of relation are maintained each time a userinvites another user to participate. The different possible accounttypes are stored in container 1034 and may for instance include “User”,“Professional User”, “Premium User”, “Account Administrator”, “SystemAdministrator”, etc. These account types are each associated withcertain access rights to the platform and with payment conditions. Thedifferent possible user relation types are memorized in container 1035.In case of a supply value chain, this may for instance be “Supplier”,“Customer”, “Stakeholder”, “Consumer”, “Advisor”, “Sector Colleague”,etc.

The collaboration data block 1040 represents the platform's core sinceit maintains all data related to messages 1041, workspaces/lists ofmessages 1042, message relations 1043, responses 1044, discussions 1045and update prompts 1046. In relation to messages, container 1041 forinstance stores the message ID, workspace ID, message type (i.e. thetype of response that is expected like for instance free text, Boolean,. . . ), the due date by which a response is expected, the legal and/orbusiness context of the message, the details (e.g. the enquiry), theunit of measure to be used for the response, and its status. Similarly,once a workspace is created and next level participants are invited,container 1042 shall maintain in a record the workspace ID, theinitiator of the workspace, the participants that are invited to theworkspace and their respective rights, the due date for responding, thelegal and business context that is shared within that workspace, andsettings enabling the platform to automatically forward messages andreminders. Further, container 1043 stores data with respect to linksbetween messages and sub-messages, like the message IDs and the type ofrelation between them. Instead of the link between message andsub-messages, the link between their initiators may be maintained or alink between their collaboration spaces may be maintained. Informationwith respect to responses is stored in data container 1044. The messageID, workspace ID and user ID of the response may for instance be stored.Similar information is maintained with respect to discussions, like chatdiscussions, in data container 1045. Again, the message ID, workspace IDand user ID related to the discussion will be memorized, together witheventual detailed text reflecting the content of the discussion. Atlast, when messages, sub-messages or responses are updated, the updateprompt container 1046 memorizes the message ID, workspace ID anddetailed text related to the update.

The collaboration data 1040 are intensively used by the work areaqueries block 1050 that queries and stores information related to theuser's work area, i.e. the GUI images that are presented to the user.For each active user and each active messages/sub-messages 1051, theuser interface options and workspace details are collected in block1050. This includes information with respect to related messages 1052 aswell upstream as downstream, workspace discussions 1053 (e.g. chatsrelated to the active message), active message discussions 1054, relateddocuments 1055, update prompts 1056, and standard responses 1057 (e.g.frequently given responses). All this information will be displayed ormade accessible in the GUI image that is generated for the activemessage. In addition, the work area block 1050 shall collect informationwith respect to the active user's contacts 1058 (like their name,relation status and activity status) and information with respect to theactive user's workspaces 1059 (like their due date or overdue days) fordisplay in the active user's workspace. Whereas the workspaceinformation 1059 may be collected from the collaboration data block1040, the contact information 1058 will be queried from the user andaccount administration block 1030. Finally, the work area block 1050generates reports 1080 for the active user that are displayed or madeaccessible through his/her work area. As is indicated by 1081 in FIG.10B, these reports may for instance be reports on overdue workspaces,reports on overdue messages, lists of messages ordered by status, listsof messages ordered by contact, reports of overdue messages ordered bycontact, or statistics like average response times per contact, etc.

From the messages and workspaces, reference can be made to variousinformation that is stored in the collaboration master and referencedata block 1060. The referenced information may include workspacetemplates 1061 (i.e. default information for establishing workspaceslike for instance the default participant rights, default context ofmessages, default settings for forwarding messages, etc.), wiki pageswhereto the text of the messages refers (e.g. the page ID and owner,privacy settings regulating for instance that only participants thathave accepted an NDA get access to the page, text details and imagedetails), default data for updates 1063 (like for instance the updatetype and text details), files or documents 1064 that are related to themessages (e.g. the file ID and owner, the privacy settings regulatingaccess to the file, the file type and details), and data with respect topredefined responses 1065 (like for instance the response ID and owner,privacy settings, text details, the unit of measure or UOM, etc.).

The solution administration block 1070 gives a non-exhaustive view ondifferent kinds of system information that may be logged in the platformaccording to the invention. Examples are activity logs 1071 of thedifferent users (wherein the login time and user ID are tracked), errorlogs 1072 (wherein the error code, user ID of users affected by theerror, time whereon the error occurred and window wherein the erroroccurred are tracked), user interface libraries 1073 (like for instancelanguage preferred by an organization or other personalization data likelogo's colors, templates, etc. used by an organization), and a help andwarning message container 1074 wherein information with respect to ahelp function of the platform is stored.

FIG. 11 illustrates a first instantiation of the collaboration methodaccording to the present invention, in line with the message flowdescribed here above with reference to FIG. 6. Initiator 158 creates amessage 168 and collaboration space 150 wherein first degree partners160, 162 and 164 are invited to collaborate on the message 168. Teammember 164 can create a sub-message 172 or S2, as well as acollaboration space 154 with second degree partners invited to work onthe sub-message 172. Team member 164 shall come back to the team 150 offirst degree partners with the contribution of the newly establishedteam 154.

FIG. 12 illustrates an alternative instantiation of the collaborationmethod according to the present invention wherein the first degreepartner that creates a sub-message does not necessarily coincide withthe person/venture that creates the team invited to collaborate on thesub-message. Again, initiator 158 is assumed to create a message 168 andcollaboration space 150 wherein first degree partners 160, 162 and 164are invited to collaborate on the message 168. This time, team member164 creates a sub-message 171 or S3, and only forwards the sub-message171 to another contributor 151. It is then up to the latter contributor151 to provide the solution himself or to establish a team that will beinvited to collaborate on the sub-message S3, forward the sub-message tothe team members, and come back to the first degree partner 164 with hiscontribution or the contribution generated through collaboration.

FIG. 13A to 13I illustrate a scenario wherein the platform and methodfor collaboration according to the current invention are exploited toresolve a customer initiated question 1303 that requires collaborationof the entire development and supply chain of a pencil with eraser.

In FIG. 13A, the customer 1301 requests the store/distributor 1302 wherehe intends to buy a pencil with eraser to explain if the pencil witheraser that is currently on sale for 0.40

is not harmful when used by his/her 6 year old boy. This question isdenoted 1303 in FIG. 13A and is entered into the platform by customer1301 via the work area shown in FIG. 14A. There, the customer 1301creates a new message by opening the window 1401 in his Home work area.By selecting the “Define question” tab 1402 in window 1401, the user canenter his enquiry in text box 1404. Through tab 1403, the user canselect the participants that are invited to respond, and contextinformation like a due date and references can be associate with themessage via tab 1404. Optionally, the buttons 1406 and 1407 allow to addattachments and add hyperlinks, finally enabling the user to create awork space for the message by clicking the button 1408. The customer1301 asks the question because he/she has heard that a lot of erasersare harmful as a result of certain chemical substances containedtherein, whereas European legislation known as REACH (Registration,Evaluation, Authorisation and Restriction of CHemical substances)regulate the use of such chemical substances and information to beprovided by industry with respect to such use.

As is shown in FIG. 13B, the store/distributor 1302 sends a response1308 to the customer 1301 thanking the customer for his/her question1303. In the response 1308, the store 1302 informs the customer 1301that all products sold are conform to EN (European Norms) andconsequently should not contain chemical substances higher than thelegally allowed limits. However, the question 1303 will be checkedparticularly for the pencil with eraser with the supplier thereof andthe store 1302 promises the customer 1301 in its response 1308 to comeback with a response.

The store/distributor 1302 that has received the request 1303 forwardsthe question to its supplier 1306 of the pencil with eraser, and invitesalso his internal REACH expert 1307 to collaborate on the issue. Thedistributor 1302 thereto creates a sub-message 1305 or S2 wherein thecustomer's question 1303 is copied, and establishes a collaborationspace 1304 where the supplier 1306 of pencils with eraser and the REACHexpert 1307 are invited to collaborate.

The supplier 1306 is supposed to be an importer of office supplies, whois getting more and more of these questions. He has contracted a REACHspecialist 1312 to help him in dealing with these requests. The suppliercreates a sub-message 1310 or S3 wherein the request 1305 received fromthe distributor is copied, and establishes a collaboration space 1309wherein his REACH specialist 1312 is invited to assist in dealing withthe question. The REACH specialist 1312 does some research and explainsthat the biggest concerns with erasers are with PVC (PolyVinyl Chloride)erasers containing the phthalate DEHP as a plasticizer. DEHP(Di-EthylHexyl Phthalate) is on the SVHC (Substances of Very HighConcern) list and can be harmful for fertility, asthma, etc. whenchildren take the eraser in their mouth. The REACH specialist 1312 alsorecommends the importer 1306 to check eventual presence of othersubstances on the SVHC list in the pencil, as well as the presence ofother phthalates in the eraser and advices to find alternatives for anyof these substances if present. The importer 1306 and his REACHspecialist 1312 decide to invite the Asian exporter 1311 of officesupplies to the collaboration space 1309 and ask the questions.

Moving to FIG. 13C, it is supposed that the exporter 1311 of the pencilsonly brands these pencils. The exporter 1311 therefore forwards therequest to the pencil manufacturer 1315 and his quality manager 1316.The exporter 1311 thereto creates a sub-message 1314 or S4 wherein therequest 1310 is copied, and establishes a collaboration space 1313wherein the pencil manufacturer 1315 and quality manager 1316 areinvited to collaborate.

The pencil manufacturer 1315 assembles the pencils and has a lot ofattention for the design, the quality of the writing of the pencils, andthe wood parts, but not for the eraser which he sources from aspecialist 1319 in yet another Asian country. He keeps part of thequestionnaire S4 but forwards the eraser question to the supplier 1319of the eraser raw material, as is indicated by FIG. 13D. The productmanager 1320 at the pencil manufacturer 1315 explores presence of SVHCsubstances or phthalates in the pencil, coating, etc. Throughsub-message 1318 or S5, the pencil manufacturer 1315 requests thesupplier 1319 of raw material of the eraser to verify if there are anyphthalates in the eraser material, as well as any other substances onthe SVHC list. The pencil manufacturer 1315 indicates that the questionis important considering the REACH legislation in Europe and invites thesupplier 1319 of raw material of the eraser to collaboration space 1317.In case of non-compliance, the European market may be lost.

After 25 days, the distributor 1302 hasn't heard anything and sends areminder to his supply chain, reminding of the fact that the EUlegislation requires a response to the customer's question 1303 within45 days. Sales of the product may be discontinued if no response isreceived from everyone involved. The distributor 1302 requests a statusupdate and confirmation that everyone in the supply chain can respondwithin the requested time.

The supplier 1319 of the eraser gets the reminder and wonders what todo. He does not know much about REACH legislation but the platformsupports contacting a couple of experts 1322 in this area. He asks whohas experience with PVC and Phthalates, and contracts a REACHconsultant. They use the chat function and some skype calls tocollaborate as is indicated by 1321 in FIG. 13D, and provide a replyback to the pencil manufacturer 1315.

The supplier 1319 of eraser raw material informs the manufacturer 1315of pencils that he is not knowledgeable in detail on REACH, but the goodnews is that all his products are phthalate free. The supplier 1319 oferaser material doesn't use DEHP, present on the REACH SVHC list, norDINP (Diisononyl Phthalate), not present on the SVHC list but also aphthalate, in his products since 2 years. The supplier 1319 of erasermaterial confirms that he also checked for other substances on the SHVClist, and declares that none of them are present in the eraser materialwith more than 0.1%.

In FIG. 13E, the manufacturer of pencils 1315 informs the Asian exporter1311 of branded pencils that the eraser is phthalate free and thuscontains no DEHP not DINP nor any other phthalates. The pencilmanufacturer 1315 further informs the exporter 1311 that none of theother SVHC substances are present with more than 0.1% in the pencileraser. The response of the pencil manufacturer is denoted 1323 in FIG.13E. To the question if the paint on the pencil can be declared nontoxic, the pencil manufacturer 1315 has no response yet but confirmsthat he is still analyzing the paint/varnish used. Answering within thetime given will not be possible, but the pencil manufacturer 1315declares to come back within approximately four weeks.

The exporter's quality manager 1316 in an internal message to theproduct manager indicates that it is good to see that the erasers arephthalate and SHVC free. For the rest of the pencil, the quality manager1316 indicates that it is safe to state that there are no SVHCsubstances present with more than 0.1% of the pencil weight, but a checkis ongoing on presence of potentially toxic substances in the pigments.If they are present, it will be less than 0.1% but at this point intime, the presence thereof can't be excluded. This is further alsoillustrated by FIG. 14B depicting the Workspace work area 1410 of theexporter's quality manager. In his work area 1410, the quality managersees the inbound messages 1411 and related sub-messages 1413 andresponses 1414. Details relating to a selected message like the contextare displayed in 1412 whereas details related to a selected response aredisplayed in 1415. The selected response 1417 or all responses 1416related to the workspace can be copied to a related message or relatedworkspace. More generally, as shown in FIG. 14C, inbound responses 1421may be displayed to the user. For a selected inbound response, e.g.Response 1, the response details 1422 and workspace participants 1423may be shown. Simultaneously, a list of related messages 1424 isvisualized and the details 1425 and workspace participants 1426 of theselected message, e.g. Message 2, are shown. As is indicated by 1427,the user is then given the opportunity to copy or amend and copy theselected response details 1422 into the selected related message details1426, or the platform may do this automatically when settings allow theplatform to do so.

in FIG. 13F, the Asian exporter 1311 of branded pencils informs theEuropean importer 1306 of office supplies that the eraser is phthalatefree and thus contains no DEHP not DINP nor any other phthalates. Noneof the other SVHC substances are present with more than 0.1% in thepencil. The paint on the pencil cannot be declare non toxic. Analysis ofthe paint/varnish is ongoing and will not be finished within the timegiven, but an answer will be available within approximately four weeks.This is indicated by arrow 1324 in FIG. 13F.

In FIG. 13G, the REACH consultant 1312 confirms via an internal message1325 to the importer 1306 of office supplies that the conclusion ispositive and the answer 1324 received from the Asian exporter 1311 canbe forwarded as it did come in.

In FIG. 13H, the importer 1306 of office supplies informs the store 1302that the eraser is phthalate free and thus contains no DEHP not DINP norany other phthalates. None of the other SVHC listed substances arepresent with more than 0.1% in the pencil. The paint on the pencilcannot yet be declared non-toxic, since analysis of the paint/varnish isongoing. Results thereof will not be available within the time given,but an answer will be given within approximately four weeks. This is thecontents of response 1326 in FIG. 13H.

The REACH coordinator 1307 informs the customer liaison at the store1302 that there are no phthalates in the eraser and as such that thestore can declare to the customer that the eraser is safe. The REACHcoordinator in an internal message to the customer liaison also mentionsthat the store has a continued improvement program on presence of anytoxic products.

In FIG. 13I, the customer liason at the store 1302 at last informs thecustomer that double checks with the suppliers have taken placeconfirming that he eraser of the pencil on sale is phthalate free. Thecustomer consequently should not worry about his/her 6 year old boyusing the eraser. This is indicated by arrow 1327.

Although the present invention has been illustrated by reference tospecific embodiments, it will be apparent to those skilled in the artthat the invention is not limited to the details of the foregoingillustrative embodiments, and that the present invention may be embodiedwith various changes and modifications without departing from the scopethereof. The present embodiments are therefore to be considered in allrespects as illustrative and not restrictive, the scope of the inventionbeing indicated by the appended claims rather than by the foregoingdescription, and all changes which come within the meaning and range ofequivalency of the claims are therefore intended to be embraced therein.In other words, it is contemplated to cover any and all modifications,variations or equivalents that fall within the scope of the basicunderlying principles and whose essential attributes are claimed in thispatent application. It will furthermore be understood by the reader ofthis patent specification that the words “comprising” or “comprise” donot exclude other elements or steps, that the words “a” or “an” do notexclude a plurality, and that a single element, such as a computersystem, a processor, or another integrated unit may fulfil the functionsof several means recited in the claims. Any reference signs in theclaims shall not be construed as limiting the respective claimsconcerned. The terms “first”, “second”, third”, “a”, “b”, “c”, and thelike, when used in the description or in the claims are introduced todistinguish between similar elements or steps and are not necessarilydescribing a sequential or chronological order. It is to be understoodthat the terms so used are interchangeable under appropriatecircumstances and embodiments of the invention are capable of operatingaccording to the present invention in other sequences different from theone(s) described or illustrated above.

1. A computer-implemented collaboration platform comprising: a clientcommunications module configured to enable an initiator to create amessage, said client communications module configured to enable saidinitiator to invite a group of first degree partners to respond to saidmessage, said client communications module configured to enable a firstdegree partner of said group of first degree partners to create asub-message; a database adapted to automatically create a link betweensaid sub-message and said message, between said first degree partner andsaid initiator, or between collaboration spaces established for saidsub-message and said message; and a collaboration module configured toenable said first degree partner to invite a group of second degreepartners to respond to said sub-message while concealing identities ofone or more first degree partner from said group of second degreepartners, concealing identities of one or more second degree partnerfrom said group of first degree partners, or both.
 2. Acomputer-implemented collaboration platform according to claim 1,wherein said initiator, said first degree partners and said seconddegree partners are partners of a value chain.
 3. A computer-implementedcollaboration platform according to claim 1, wherein said sub-messagefurther comprises: a copy of said message; a copy of part of saidmessage; a modified copy of said message; a modified copy of part ofsaid message; or a related message.
 4. A computer-implementedcollaboration platform according to claim 1, wherein said clientcommunications module is configured to enable said initiator to addattributes to said message.
 5. A computer-implemented collaborationplatform according to claim 4, wherein said attributes further comprisea due date for responding to said message.
 6. A computer-implementedcollaboration platform according to claim 4, wherein said attributesfurther comprise a legal context for said message.
 7. Acomputer-implemented collaboration platform according to claim 4,wherein said attributes further comprise a business context for saidmessage.
 8. A computer-implemented collaboration platform according toclaim 1, wherein said client communications module is configured toenable an initiator to create a list of messages containing saidmessage, and said client communications module configured to enable saidinitiator to invite a group of first degree partners to respond to saidlist of messages.
 9. A computer-implemented collaboration platformaccording to claim 1, further comprising a client work modulecomprising: a first group of graphical user interface elements adaptedto present options on inbound messages; a second group of graphical userinterface elements adapted to present options on outbound messages; athird group of graphical user interface elements adapted to presentoptions on inbound responses; and a fourth group of graphical userinterface elements adapted to compose an outbound response.
 10. Acomputer-implemented collaboration platform according to claim 9,wherein said options on inbound responses further comprise: said inboundresponse copied to an outbound response; said inbound response modifiedand copied to an outbound response; an outbound response edited orcreated with the use of a related inbound response in a side-by-sidewindow; or combinations thereof.
 11. A computer-implementedcollaboration platform according to claim 1, further comprising a clientlibrary module comprising: a data store adapted to store a user-specifichistory of inbound and outbound messages and responses.
 12. A method foranonymous collaboration comprising: creating a message by an initiator;said initiator inviting a group of first degree partners to respond tosaid message; and a first degree partner of said group of first degreepartners creating a sub-message; automatically creating a link betweensaid sub-message and said message, between said first degree partner andsaid initiator, or between collaboration spaces established for saidsub-message and said message; and said first degree partner inviting agroup of second degree partners to respond to said sub-message whileconcealing identities of one or more first degree partner for said groupof second degree partners, concealing identities of one or more seconddegree partner for said group of first degree partners, or both.
 13. Acomputer implemented system, comprising: a message accessible at leastto a creating user of the message and to each member of an initialinvited user group, the initial invited user group comprising one ormore users invited to access the message; one or more sub-messages ofthe message, each sub-message of the one or more sub-messages beingaccessible at least to a creating user of the sub-message and to eachmember of an additional invited user group, the additional invited usergroup comprising one or more users invited to access the sub-message; aninitial plurality of permissions controlling access to the message, theinitial plurality of permissions comprising one or more automaticallyassigned permissions enabling the creating user of the message to sendinvitations to access the message, and further comprising one or moreadditional permissions that either permit or deny each member of theinitial invited user group the ability to create one or more additionalsub-messages of the message; for each of the one or more sub-messages,an additional plurality of permissions controlling access thereto, theadditional plurality of permissions comprising one or more automaticallyassigned permissions enabling the creating user of the sub-message tosend invitations to access the sub-message, and further comprising oneor more additional permissions that either permit or deny each member ofthe additional invited user group the ability to create one or moreadditional sub-messages of the message; wherein the system enables theidentity of each member of any invited user group to be concealed fromany member of any different invited user group.
 14. The computerimplemented system of claim 13, further comprising, for each of themessage and the one or more sub-messages of the message, one or morecommunication mechanisms for enabling communication among any members ofeach invited user group and the creating user.
 15. The computerimplemented system of claim 13, wherein any creating user of the one ormore sub-messages of the message is enabled to submit a response. 16.The computer implemented system of claim 15, wherein the responsecomprises any one or more of an answer, a confirmation, additionalinput, a question, or a reply.
 17. The computer implemented system ofclaim 13, wherein the identity of each member of at least one inviteduser group is concealed from any member of any different invited usergroup.
 18. The computer implemented system of claim 13, wherein theidentity of each member of at least one invited user group is notconcealed from the members of one or more different invited user group.19. The computer implemented system of claim 13, wherein each of the oneor more sub-messages is created either from the message or from apreceding sub-message of the one or more sub-messages, and furtherwherein each sub-message comprises a modified or unmodified copy ofeither the message or the preceding sub-message from which it wascreated.
 20. The computer implemented system of claim 13, wherein eachsub-message of the one or more sub-messages is created either from themessage or from a preceding sub-message of the one or more sub-messages,and further wherein each sub-message comprises all or a subset of eitherthe message or the preceding sub-message from which the sub-message wascreated.
 21. The computer implemented system of claim 13, wherein themessage and the one or more sub-messages form at least one of a datachain, the data chain comprising a set of successively linked datacopies, wherein a first data copy of the set of successively linked datacopies comprises the message and further wherein each successive datacopy of the set of successively linked data copies comprises one of theone or more sub-messages.